Service Level Dashboard 2.0 for 
System Center Operations Manager 2007 R2 RC1
Release Notes
May, 2009
© 2009 Microsoft Corporation. All rights reserved.

Contents
§1. Download and on-line locations 
§2. Brief description of Service Level Dashboard
§3. What’s new in v2.0
§4. Contents of download package
§5.  Prerequisites
§6. Installation instructions
§7. Known issues

§1. Download and on-line locations 
•	Download: http://go.microsoft.com/fwlink/?Linkid=40288
•	TechNet online (summary information only): http://go.microsoft.com/fwlink/?linkid=110335

§2. Brief description of Service Level Dashboard
The Service Level Dashboard 2.0 for System Center Operations Manager 2007 R2 addresses the need for managers, application owners, and IT pros to ensure that their resources (applications and systems) are available and performing at acceptable levels. It does this by tracking and reporting on adherence to service level commitments for line-of-business (LOB) applications. Results are displayed in a single Web-based user interface.

§3. What’s new in v2.0
Version 2.0 of the Service Level Dashboard for System Center Operations Manager 2007 R2 includes the following changes from the previous version.
•	Near real-time data latency. The data latency is now near real-time at two to three minutes.
•	Dashboard metrics for service level tracking. New metrics facilitate the tracking of MTTR, MTBF, and application service level trends.
•	Service Level Objectives (SLOs). Version 2.0 uses the new Service Level Tracking feature of Operations Manager to configure service goals for applications and groups
•	New presentation platform. Version 2.0 uses Windows SharePoint Services 3.0 SP1 as its presentation platform.
•	Authentication. Version 2.0 uses Windows SharePoint Services groups to authenticate its users and sites.
§4. Contents of download package
The download is available as a single zip file, packaged as follows:

  Service Level Dashboard 2.0.zip
	SLD 2.0 Release Notes.rtf (this document)
	Microsoft.EnterpriseServiceMonitoring.ServiceLevelDashboard.R2.mp
	Service Level Dashboard 2.0_x86.msi
	Service Level Dashboard 2.0_x64.msi
 	Documentation
	Service Level Dashboard 2.0 for Operations Manager 2007 R2 User Guide.doc
	Supplemental License for Service Level Dashboard for OpsMgr 2007 R2.rtf

§5. Prerequisites
The following table lists software requirements for the dashboard.
Table 1. Service Level Dashboard 2.0 Software Requirements
Infrastructure | Resource

Software

•	Operations Manager 2007 R2 with Reporting and Data Warehouse
•	Windows SharePoint Services 3.0 SP1
Note   Microsoft Office SharePoint Server 2007 SP1 is supported as an alternative to Windows SharePoint Services 3.0.  
•	SQL Server 2005 SP2 or SQL Server 2008.
Note   Typically, WSS and MOSS installations install SQL Server Embedded Edition, which does not meet the Service Level Dashboard requirement to create SLD content database. 
•	Microsoft .NET Framework 3.5

Browser

•	Microsoft Internet Explorer® 6.0 or Internet Explorer 7.0. 
Note   The Service Level Dashboard has not been tested on Internet Explorer 8.0.

Important   Service Level Dashboard 2.0 integrates with an already functioning deployment of Microsoft® System Center Operations Manager 2007 R2 and has no unique hardware requirements. It is assumed that Operations Manager 2007 R2 and its Data Warehouse database are configured in accordance with Microsoft installation guidance. 

§6. Installation instructions
To install Service Level Dashboard 2.0 for System Center Operations Manager 2007 R2 

1.	Download the .zip file Service Level Dashboard 2.0.zip to your computer.
2.	Copy the Management Pack from the location you specified during download to the Operations Manager management server.  
Note This management pack is essential to update the stored procedures required for SLD functionality.
3.	In the Operations Manager Operations console, from the Administration view, click Management Packs and choose Import Management Pack.
4.	Follow the instructions to import the Management Pack. The file name is Microsoft.EnterpriseServiceMonitoring.ServiceLevelDashboard.R2.MP.
5.	After the import process is complete and the dialog box displays an icon next to the management pack indicating success or failure of the importation, click Close.
6.	Copy the ServiceLevelDashboardV2_x86.msi or ServiceLevelDashboardV2_x64.msi (whichever one is appropriate for your system) file from the location you specified during download to a Windows SharePoint Server that has SharePoint 3.0 Central Administration installed.
7.	Run the .msi file to begin the installation process.
8.	Follow the steps in the installation wizard, which will prompt for the following information:
User Input Parameter | Description | Format

Operations Manager Username

Application pool identity (should be a domain user). 
Note   SLD installation sets this user credential for the application pool in IIS.  It also creates a SLDReader Role on the Operations Manager Data Warehouse database and assigns the user account to the SLDReader Role.

Domain\UserName

Operations Manager User Password | Password, for login to Operations Manager. |

Operations Manager Data Warehouse Server Name

Operations Manager Data Warehouse server

Server name\InstanceName
(If SQL Server is installed on the default instance,  specify only the Server Name for this property)

Operations Manager Data Warehouse Database Name | Operations Manager Data Warehouse database | Database Name
Site Owner’s Login Name | User account for the SharePoint site administrator | Domain\UserName
Site Owner’s E-mail address | E-mail address for the SharePoint administrator | email@contoso.com

SharePoint Database Server Name

Windows SharePoint Services content database server name

Server name\Instance Name
(If SQL Server is installed on the default instance,  specify only the Server Name for this property)

SharePoint Session Database Name | Windows SharePoint Services content database name | Database Name

Service Level Dashboard SharePoint Site URL

The URL for the SharePoint site being created. 
Example: http://servername:51918

http://<server name>:<port number>
Note   Do not use localhost for server name. Instead use the actual name of the server / IP address. If localhost is specified for Server Name, users may not be able to access the dashboard from other machines by navigating to http://<ServerName>:<PortNumber>. Instead they will have to use http://<ServerName>:<PortNumber>/Default.aspx

9.	When you receive a message that indicates the Gauge Controls, Site Template and Web Parts are installed successfully, click Close.
Note  The Dashboard is designed for best view at screen resolution settings of 1280 by 1024 pixels.

§7. Known issues
Service Level Dashboard cannot install successfully when you try to use SQL Server Embedded Edition for creating the SharePoint content database.  
Typically, WSS and MOSS installations install SQL Server Embedded Edition, which does not meet the Service Level Dashboard requirement to create SLD content database. You need to install SQL Server 2005 SP2 or SQL Server 2008 to complete installation successfully.

Service Level Dashboard will fail when you use a remote SharePoint Server name for the URL parameter during setup
Using a remote SharePoint Server Name for the URL parameter during setup means you are trying to install the Service Level Dashboard on a remote SharePoint server. The remote installation scenario is not supported.  You need to run the installation on a local SharePoint Server and specify the server name in the URL parameter.

Service Level Dashboard will fail when you try to install without administrative privileges
Service Level Dashboard installation will configure permissions on Operations Manager Data Warehouse database and on the SharePoint Server database.  You need to run the installation with administrative privileges in order to complete the installation successfully.

Service Level Dashboard will fail to render when you use https during installation unless you configure the binding in IIS
Http is the default protocol configuration value for the dashboard URL parameter during setup. If you intend to use https, you need to configure the binding after setup.  
To configure an HTTPS binding
1.	Open IIS Manager. 
2.	In the Connections pane, expand the Sites node in the tree, and then click to select the site for which you want to add a binding.
3.	In the Actions pane, click Bindings.
4.	In the Site Bindings dialog box, click Add.
5.	In the Add Site Binding dialog box, on the Type menu, select https.
6.	In the SSL Certificate list, select the entry that matches the name of your computer, and then click OK.
7.	In the Site Bindings dialog box, click Close.
8.	In the Connections pane, under Default Web Site, click CertSrv.
9.	In the /CertSrv Home pane, right-click SSL Settings, and then click Open Feature.
10.	In the SSL Settings pane, click Require SSL and then click Require 128-bit SSL.

On computers with insufficient memory or processor, you may get the following error intermittently
Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not 
be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), 
response filters, HttpModules, or server trace is enabled. Details: Error parsing near '<HTML dir="ltr"><H'
When this issue occurs and you receive the error message, the UI will freeze. The work around is to refresh or restart the IE browser.